Automatically updating a hybrid application

ABSTRACT

Disclosed are systems, methods, and non-transitory computer-readable storage media for automatically updating a hybrid web application. In some implementations, a computing device can be configured with a hybrid application that includes a native layer and a web view. The native layer can provide access to native features of the computing device while the web view can provide web client features, such as graphical user interfaces and server communication functionality. When the hybrid application is invoked, the native layer can load a resource bundle from local storage. The resource bundle can include the web code needed to present the web view graphical user interface, manage application data, and/or facilitate communication with the web server. To update the hybrid application, the application can download an updated resource bundle from the web server and reload the web code from the resource bundle.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application Ser.No. 62/324,832, filed Apr. 19, 2016, the content of which isincorporated herein by reference in its entirety.

BACKGROUND

Much of today's computer technology is built within websites accessiblethrough web clients. For example, some websites and web clients providefor content creation, collaboration, and storage. However, purely webbased systems have limitations. For example, in order for the user touse the web client to create new content items, the user's computingdevice must be online and connected to the content creation website.Moreover, web clients are limited with respect to interactions with theuser's computing device. For example, web clients have limits on thetypes of interactions and/or amount of data that the web client canstore on the user's computing device. However, writing native clientside code that performs the same functions as the web client without thelimitations would be a burdensome task. Thus, it would be beneficial tohave a hybrid client application that can avoid the limitations of theweb client while also being able to operate while the user's device isoffline.

SUMMARY

Additional features and advantages of the disclosure will be set forthin the description which follows, and in part will be obvious from thedescription, or can be learned by practice of the herein disclosedprinciples. The features and advantages of the disclosure can berealized and obtained by means of the instruments and combinationsparticularly pointed out in the appended claims. These and otherfeatures of the disclosure will become more fully apparent from thefollowing description and appended claims, or can be learned by thepractice of the principles set forth herein.

Disclosed are systems, methods, and non-transitory computer-readablestorage media for automatically updating a hybrid web application. Insome implementations, a computing device can be configured with a hybridapplication that includes a native layer and a web view. The nativelayer can provide access to native features of the computing devicewhile the web view can provide web client features, such as graphicaluser interfaces and server communication functionality. When the hybridapplication is invoked, the native layer can load a resource bundle fromlocal storage. The resource bundle can include the web code needed topresent the web view graphical user interface, manage application data,and/or facilitate communication with the web server. To update thehybrid application, the application can download an updated resourcebundle from the web server and reload the web code from the resourcebundle.

Disclosed are systems, methods, and non-transitory computer-readablestorage media for providing access to a hybrid web application offline.In some implementations, a computing device can be configured with ahybrid application that includes a native layer and a web view. Thenative layer can provide access to native features of the computingdevice while the web view can provide web client features, such asgraphical user interfaces and server communication functionality. Whenthe computing device is offline and the hybrid application is invoked,the native layer can load from local storage a resource bundle includingthe web code needed to present the web view graphical user interface,and/or facilitate communication with the web server. Similarly, when thecomputing device is offline, the hybrid application can load previouslystored content items into the web view from local storage through thenative layer so that the user can work with the content items offline.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-recited and other advantages and features of the disclosurewill become apparent by reference to specific embodiments thereof whichare illustrated in the appended drawings. Understanding that thesedrawings depict only example embodiments of the disclosure and are nottherefore to be considered to be limiting of its scope, the principlesherein are described and explained with additional specificity anddetail through the use of the accompanying drawings in which:

FIG. 1 shows an example configuration of devices and a network inaccordance with some embodiments;

FIG. 2 is a block diagram of an example system for updating a hybridapplication and providing access to a hybrid application offline;

FIG. 3 is a block diagram of an example system that provides a nativebridge between the native layer and web view of a hybrid application;

FIG. 4 is a component interaction diagram illustrating an exampleprocess for updating a hybrid application;

FIG. 5 is a component interaction diagram illustrating an exampleprocess for native file storage in hybrid application;

FIG. 6 is a component interaction diagram illustrating an exampleprocess for working offline in hybrid application;

FIG. 7 is an example process for updating a hybrid application;

FIG. 8 is an example process for providing access to a hybridapplication offline;

FIG. 9A shows an example possible system embodiment for implementingvarious embodiments of the present technology; and

FIG. 9B shows an example possible system embodiment for implementingvarious embodiments of the present technology.

DETAILED DESCRIPTION

Various embodiments of the disclosure are discussed in detail below.While specific implementations are discussed, it should be understoodthat this is done for illustration purposes only. A person skilled inthe relevant art will recognize that other components and configurationsmay be used without parting from the spirit and scope of the disclosure.

The disclosed technology addresses the need in the art for aself-updating hybrid mobile application that can be used even when thehosting mobile device is offline.

With respect to implementing various embodiments of the disclosedtechnology, an example system configuration 100 is shown in FIG. 1,wherein electronic devices communicate via a network for purposes ofexchanging content and other data. The system can be configured for useon a wide area network such as that illustrated in FIG. 1. However, thepresent principles are applicable to a wide variety of networkconfigurations that facilitate the intercommunication of electronicdevices. For example, each of the components of system 100 in FIG. 1 canbe implemented in a localized or distributed fashion in a network.

In system 100, a user can interact with content management system 106(e.g., an online synchronized content management system) through clientdevices 102 ₁, 102 ₂, . . . , 102 _(n) (collectively “102”) connected tonetwork 104 by direct and/or indirect communication. Content managementsystem 106 can support connections from a variety of different clientdevices, such as: desktop computers; mobile computers; mobilecommunications devices, e.g. mobile phones, smart phones, tablets; smarttelevisions; set-top boxes; and/or any other network enabled computingdevices. Client devices 102 can be of varying type, capabilities,operating systems, etc. Furthermore, content management system 106 canconcurrently accept connections from and interact with multiple clientdevices 102.

A user can interact with content management system 106 via a client-sideapplication installed on client device 102 _(i). In some embodiments,the client-side application can include a content management systemspecific component. For example, the component can be a stand-aloneapplication, one or more application plug-ins, and/or a browserextension. However, the user can also interact with content managementsystem 106 via a third-party application, such as a web browser, thatresides on client device 102 _(i) and is configured to communicate withcontent management system 106. In either case, the client-sideapplication can present a user interface (UI) for the user to interactwith content management system 106. For example, the user can interactwith the content management system 106 via a client-side applicationintegrated with the file system or via a webpage displayed using a webbrowser application.

Content management system 106 can enable a user to store content items,as well as perform a variety of content management tasks, such asretrieve, modify, browse, and/or share the content items. Furthermore,content management system 106 can enable a user to access the contentfrom multiple client devices 102. For example, client device 102 ₁ canupload content to content management system 106 via network 104. Later,the same client device 102 _(i) or some other client device 102 _(j) canretrieve the content from content management system 106.

To facilitate the various content management services, a user can createan account with content management system 106. User account database 150can maintain the account information. User account database 150 canstore profile information for registered users. In some cases, the onlypersonal information in the user profile can be a username and/or emailaddress. However, content management system 106 can also be configuredto accept additional user information such as birthday, address, billinginformation, etc.

User account database 150 can include account management information,such as account type (e.g. free or paid), usage information, (e.g. fileedit history), maximum storage space authorized, storage space used,content storage locations, security settings, personal configurationsettings, content sharing data, etc. Account management module 124 canbe configured to update and/or obtain user account details in useraccount database 150. The account management module 124 can beconfigured to interact with any number of other modules in contentmanagement system 106.

An account can be used to store content items, such as digital data,documents, text files, audio files, video files, etc., from one or moreclient devices 102 authorized on the account. The content items can alsoinclude collections for grouping content items together with differentbehaviors, such as folders, playlists, albums, etc. For example, anaccount can include a public folder that is accessible to any user. Thepublic folder can be assigned a web-accessible address. A link to theweb-accessible address can be used to access the contents of the publicfolder. In another example, an account can include: a photos collectionthat is intended for photos and that provides specific attributes andactions tailored for photos; an audio collection that provides theability to play back audio files and perform other audio relatedactions; or other special purpose collection. An account can alsoinclude shared collections or group collections that are linked with andavailable to multiple user accounts. The permissions for multiple usersmay be different for a shared collection.

The content items can be stored in content storage 160. Content storage160 can be a storage device, multiple storage devices, or a server.Alternatively, content storage 160 can be a cloud storage provider ornetwork storage accessible via one or more communications networks.Content management system 106 can hide the complexity and details fromclient devices 102 so that client devices 102 do not need to knowexactly where or how the content items are being stored by contentmanagement system 106. In some embodiments, content management system106 can store the content items in the same collection hierarchy as theyappear on client device 102 _(i). However, content management system 106can store the content items in its own order, arrangement, or hierarchy.Content management system 106 can store the content items in a networkaccessible storage (NAS) device, in a redundant array of independentdisks (RAID), etc. Content storage 160 can store content items using oneor more partition types, such as FAT, FAT32, NTFS, EXT2, EXT3, EXT4,HFS/HFS+, BTRFS, and so forth. Content storage 160 can also storemetadata describing content items, content item types, and therelationship of content items to various accounts, collections, orgroups. The metadata for a content item can be stored as part of thecontent item or can be stored separately. In one variation, each contentitem stored in content storage 160 can be assigned a system-wide uniqueidentifier.

Content storage 160 can decrease the amount of storage space required byidentifying duplicate content items or duplicate segments of contentitems. Instead of storing multiple copies, content storage 160 can storea single copy and then use a pointer or other mechanism to link theduplicates to the single copy. Similarly, content storage 160 can storecontent items more efficiently, as well as provide the ability to undooperations, by using a content item version control that tracks changesto content items, different versions of content items (includingdiverging version trees), and a change history. The change history caninclude a set of changes that, when applied to the original content itemversion, produce the changed content item version.

Content management system 106 can be configured to support automaticsynchronization of content items from one or more client devices 102.The synchronization can be platform agnostic. That is, the content itemscan be synchronized across multiple client devices 102 of varying type,capabilities, operating systems, etc. For example, client device 102_(i) can include client software, which synchronizes, via asynchronization module 132 at content management system 106, content inclient device 102 _(i)'s file system with the content in an associateduser account. In some cases, the client software can synchronize anychanges to content in a designated collection and its sub-collections,such as new, deleted, modified, copied, or moved content items orcollections. The client software can be a separate software application,can integrate with an existing content management application in theoperating system, or some combination thereof. In one example of clientsoftware that integrates with an existing content managementapplication, a user can manipulate content items directly in a localcollection, while a background process monitors the local collection forchanges and synchronizes those changes to content management system 106.Conversely, the background process can identify content items that havebeen updated at content management system 106 and synchronize thosechanges to the local collection. The client software can providenotifications of synchronization operations, and can provide indicationsof content statuses directly within the content management application.Sometimes client device 102 _(i) may not have a network connectionavailable. In this scenario, the client software can monitor the linkedcollection for content item changes and queue those changes for latersynchronization to content management system 106 when a networkconnection is available. Similarly, a user can manually start, stop,pause, or resume synchronization with content management system 106.

A user can view or manipulate content via a web interface generated andserved by user interface module 122. For example, the user can navigatein a web browser to a web address provided by content management system106. Changes or updates to content in the content storage 160 madethrough the web interface, such as uploading a new version of a contentitem, can be propagated back to other client devices 102 associated withthe user's account. For example, multiple client devices 102, each withtheir own client software, can be associated with a single account andcontent items in the account can be synchronized between each of themultiple client devices 102.

Content management system 106 can include a communications interface 120for interfacing with various client devices 102, and can interact withother content and/or service providers 109 ₁, 109 ₂, . . . , 109 _(n)(collectively “109”) via an Application Program Interface (API). Certainsoftware applications can access content storage 160 via an API onbehalf of a user. For example, a software package, such as an apprunning on a smartphone or tablet computing device, can programmaticallymake calls directly to content management system 106, when a userprovides credentials, to read, write, create, delete, share, orotherwise manipulate content. Similarly, the API can allow users toaccess all or part of content storage 160 through a web site.

Content management system 106 can also include authenticator module 126,which can verify user credentials, security tokens, API calls, specificclient devices, and so forth, to ensure only authorized clients andusers can access content items. Further, content management system 106can include analytics module 134 module that can track and report onaggregate file operations, user actions, network usage, total storagespace used, as well as other technology, usage, or business metrics. Aprivacy and/or security policy can prevent unauthorized access to userdata stored with content management system 106.

Content management system 106 can include sharing module 130 formanaging sharing content publicly or privately. Sharing content publiclycan include making the content item accessible from any computing devicein network communication with content management system 106. Sharingcontent privately can include linking a content item in content storage160 with two or more user accounts so that each user account has accessto the content item. The sharing can be performed in a platform agnosticmanner. That is, the content can be shared across multiple clientdevices 102 of varying type, capabilities, operating systems, etc. Thecontent can also be shared across varying types of user accounts.

In some embodiments, content management system 106 can be configured tomaintain a content directory identifying the location of each contentitem in content storage 160. The content directory can include a uniquecontent entry for each content item stored in the content storage.

A content entry can include a content path that can be used to identifythe location of the content item in a content management system. Forexample, the content path can include the name of the content item and afolder hierarchy associated with the content item. For example, thecontent path can include a folder or path of folders in which thecontent item is placed as well as the name of the content item. Contentmanagement system 106 can use the content path to present the contentitems in the appropriate folder hierarchy.

A content entry can also include a content pointer that identifies thelocation of the content item in content storage 160. For example, thecontent pointer can include the exact storage address of the contentitem in memory. In some embodiments, the content pointer can point tomultiple locations, each of which contains a portion of the contentitem.

In addition to a content path and content pointer, a content entry canalso include a user account identifier that identifies the user accountthat has access to the content item. In some embodiments, multiple useraccount identifiers can be associated with a single content entryindicating that the content item has shared access by the multiple useraccounts.

To share a content item privately, sharing module 130 can be configuredto add a user account identifier to the content entry associated withthe content item, thus granting the added user account access to thecontent item. Sharing module 130 can also be configured to remove useraccount identifiers from a content entry to restrict a user account'saccess to the content item.

To share content publicly, sharing module 130 can be configured togenerate a custom network address, such as a uniform resource locator(URL), which allows any web browser to access the content in contentmanagement system 106 without any authentication. To accomplish this,sharing module 130 can be configured to include content identificationdata in the generated URL, which can later be used to properly identifyand return the requested content item. For example, sharing module 130can be configured to include the user account identifier and the contentpath in the generated URL. Upon selection of the URL, the contentidentification data included in the URL can be transmitted to contentmanagement system 106 which can use the received content identificationdata to identify the appropriate content entry and return the contentitem associated with the content entry.

In addition to generating the URL, sharing module 130 can also beconfigured to record that a URL to the content item has been created. Insome embodiments, the content entry associated with a content item caninclude a URL flag indicating whether a URL to the content item has beencreated. For example, the URL flag can be a Boolean value initially setto 0 or false to indicate that a URL to the content item has not beencreated. Sharing module 130 can be configured to change the value of theflag to 1 or true after generating a URL to the content item.

In some embodiments, sharing module 130 can also be configured todeactivate a generated URL. For example, each content entry can alsoinclude a URL active flag indicating whether the content should bereturned in response to a request from the generated URL. For example,sharing module 130 can be configured to only return a content itemrequested by a generated link if the URL active flag is set to 1 ortrue. Thus, access to a content item for which a URL has been generatedcan be easily restricted by changing the value of the URL active flag.This allows a user to restrict access to the shared content item withouthaving to move the content item or delete the generated URL. Likewise,sharing module 130 can reactivate the URL by again changing the value ofthe URL active flag to 1 or true. A user can thus easily restore accessto the content item without the need to generate a new URL.

While content management system 106 is presented with specificcomponents, it should be understood by one skilled in the art, that thearchitectural configuration of system 106 is simply one possibleconfiguration and that other configurations with more or fewercomponents are possible.

FIG. 2 is a block diagram of an example system 200 for updating a hybridapplication and providing access to a hybrid application offline. Forexample, system 200 can correspond to system 100 of FIG. 1. System 200can include content management system 106, as described above.

In some implementations, content management system 106 can includecontent authoring module 202. For example, content authoring module 202can provide features for creating content items and/or collaborating oncontent items. A user of system 200 can, for example, use a web browserto access content authoring module 202. Content authoring module 202 candeliver client resource bundle 204 to the web browser on the user'sdevice. Client resource bundle 204 can include web code (e.g., HTML,JavaScript, etc.) for presenting a client interface of content authoringmodule 202. For example, client resource bundle 204 can include web codethat causes the browser to present a text editing graphical userinterface (e.g., a word processor) that the user can interact with toview and/or edit a textual content item. After the user creates or editsa content item using content authoring module 202, content authoringmodule 202 can store the created or edited content item in contentstorage 160. After the content item is stored in content storage 160,the content item can be synchronized between user devices, shared withother users and/or managed by content management system 106 similarly toother content items, as described above with reference to FIG. 1.

In some implementations, system 200 can include mobile device 210. Forexample, mobile device 210 can correspond to client device 102 _(i) ofFIG. 1. In some implementations, mobile device 210 can include contentauthoring application 212. For example, instead of using a browser basedweb client to access content authoring module 202, as described above,the user of mobile device 210 can download and install content authoringapplication 212 on mobile device 210 to access the features and/orfunctionality provided by content authoring module 202.

In some implementations, content authoring application 212 can be ahybrid mobile application. For example, content authoring application212 can include native layer 214. Native layer 214 can be an executableobject compiled for execution on a particular computing platform. Forexample, native layer 214 can be compiled or built for execution onmobile device 210 (e.g., built for the operating system, processor,chipset, etc.) or devices having a similar configuration as mobiledevice 210. Because native layer 214 is built to run on mobile device210, native layer 214 can have access to system functions and featuresof mobile device 210 that a browser based client does not while alsoperforming better than non-native software. For example, while a browserbased client of content authoring module 202 may be restricted as towhich native or system functions the browser based client can access orthe size of files that the browser based client can store, native layer214 does not have those same restrictions because the native layer isbuilt to interact natively with the operating system of mobile device210 to access the system functions of mobile device 210.

In some implementations, content authoring application 212 can includeweb view 216. For example, web view 216 can be a web browser that isbundled inside of native layer 214. Native layer 214 can, for example,be a container for web view 216. Thus, web view 2016 can read,interpret, compile, and/or execute web code and/or technologies, such asHTML, JavaScript, cascading style sheets, etc., to generate graphicaluser interfaces, communicate with web servers, and perform other webclient functions. The specific functionality of web view 216 depends onthe web code loaded by web view 216.

Continuing the content authoring example above, a user of mobile device210 can invoke content authoring application 212 to create, edit,collaborate on, or otherwise interact with content items. For example,when content authoring application 212 is invoked on mobile device 210,the code in native layer 214 can be executed.

Upon invocation of content authoring application 212, native layer 214can load client resource bundle 220. For example, instead of downloadingclient resource bundle 204 from content management system 106 each timethe user invokes content authoring application 212, content authoringapplication 212 can download and store a local copy of client resourcebundle 204 (e.g., local client resource bundle 220). For example, clientresource bundle 220 can be downloaded and stored on mobile device whencontent authoring application 212 is initially downloaded and installedon mobile device 212. Subsequently, content authoring application 212can automatically download and store updates to client resource bundle220 when updates are available from content management system 106, asdescribed further below. Storing a local copy of client resource bundle220 can, for example, facilitate offline use of content authoringapplication 212, as described further below.

In some implementations, client resource bundle 220 can include nativeconfiguration 222. For example, native configuration 222 can identifythe current version of content authoring application 212 installed onmobile device 210. Native configuration 222 can include a URL forreceiving new messages from the web code executed by web view 216(described further below). Native configuration 222 can identifyresources needed to run the identified version of content authoringapplication 212.

In some implementations, client resource bundle 220 can includeresources 226. For example, resources 226 can include the files (e.g.,web code files, JavaScript files, HTML files, images, icons, etc.)containing the computer instructions for executing web view 216. Forexample resources 226 can include the resources necessary for runningthe web client for content authoring module 202 in web view 216. Forexample, the web client run in web view 216 can be similar to the webclient run in a web browser. However, instead of being executed withinthe web browser, the web client (or portions of the web client) can berun within native layer 214 of content authoring application 212 therebyallowing the web client access to native features, functions,application programming interfaces, etc., of mobile device 210.

In some implementations, client resource bundle 220 can include nativewrapper 228. For example, native wrapper 228 can be an HTML file that isloaded into the web view 216 to boot up content authoring application212. For example, upon invocation of content authoring application 212,native layer 214 can be executed. Native layer 214 can includeinstructions for executing web view 216. When web view 216 is executedby native layer 214, web view 216 can load native wrapper 228 (e.g., anHTML file) that includes instructions for loading resources 226 (e.g.,JavaScript) from client resource bundle 228. Resources 226 can includeinstructions (e.g., JavaScript instructions, HTML instructions, CSSinstructions, etc.) for presenting graphical user interfaces (e.g., acontent editor interface), managing application data, and/orcommunicating with content authoring module 202 of content managementsystem 106. Thus, web view 216 can present graphical user interfaces,manage application data, etc., even when mobile device 210 is offlineand not connected to content authoring module 202.

In some implementations, mobile device 210 can include content storage220. For example, to facilitate use of content authoring application 212while mobile device 210 is offline and not connected to contentauthoring module 202 of content management system 106, content authoringapplication 212 can download authored content from content managementsystem 106. For example, when connected to content authoring module 202through network 104, content authoring application 212 can request fromcontent authoring module 202 content items that have been created,edited, and/or managed by content authoring module 202. When therequested content items are received by content authoring application212, content authoring application 212 can store the content items incontent storage 220. Later, when content authoring application 212 isinvoked while mobile device 210 is offline and not connected to contentauthoring module 202, content authoring application 212 can allow theuser to view and/or interact with content items in content storage 220using the content authoring interfaces provided by web view 216. Thus,content authoring application 212 can provide access to the web clientinterfaces and/or online content even when mobile device 210 is offline.

FIG. 3 is a block diagram of an example system 300 that provides anative bridge between the native layer and web view of a hybridapplication. For example, native bridge 302 can include a globalvariable (e.g., “Bridge”), an empty iframe (e.g., HTML inline frame),and a native bridge protocol for conveying messages between native layer214 and web view 216.

In some implementations, content authoring application 212 can use aglobal variable to send messages from native layer 214 to web view 216.For example, when web view 216 loads and executes the web code inresource bundle 220, the web code (e.g., JavaScript) can create a globalvariable (e.g., “Bridge”) for sending messages between native layer 214to web view 216 (e.g., the web code running in the web view). Nativelayer 214 can, for example, send messages to web view 216 by generatinga string encoded with the message to be sent to web view 216 and savingthe string in the global variable (e.g., using a JavaScript functioncall). When native layer 214 stores the message in the global variable,web view 216 can be notified that the value of the global variable haschanged. Web view 216 can then read the message and perform an operationin response to receiving the message.

In some implementations, content authoring application 212 can use anempty HTML iframe to send messages from web view 216 to native layer214. For example, when web view 216 loads and executes the web code inresource bundle 220, the web code (e.g., JavaScript) can create an emptyiframe for notifying native layer 214 that a new message has been sentfrom web view 216. Web view 216 can, for example, send messages tonative layer 214 by generating a string encoded with the message to besent to native layer 214 and saving the string in the global variable(e.g., using a JavaScript function call). When web view 216 stores themessage in the global variable, web view 216 can notify native layer 214that the value of the global variable has changed by navigating theiframe to a predefined URL (e.g., “data://_QUEUE_MESSAGE_”). Nativelayer 214 can intercept the navigation to the predefined URL andinterpret the navigation as a notice that a new message is availablefrom web view 216. Native layer 214 can then read the message from theglobal variable (e.g., using a JavaScript function call) and perform anoperation in response to receiving the message. Thus, although contentauthoring application 212 is built from heterogeneous layers implementedusing different technologies (e.g., native layer 214 implemented innative code and web view 216 implemented in non-native web code), thesedifferent layers are able to achieve bidirectional communication usingnative bridge 302, as described above.

In some implementations, content authoring application 212 can beconfigured to use native layer 214 for system interfacing features andweb view 216 (e.g., defined by web code in resource bundle 220) for userand network interfacing features. For example, native layer 214 can beconfigured to perform local data storage and retrieval functions forcontent authoring application 212 using native APIs of mobile device210. For example, when a user creates a new content item using thecontent authoring features of web view 216, web view 216 can send amessage to native layer 216 through native bridge 302 to cause nativelayer 214 to store the newly created content item to local contentstorage 220. In some implementations, web view 216 can convert thecontent item to a string and send the string to native layer 214 forstorage using native bridge 302, as described above. Thus, even if thesize of the newly created content item exceeds the data storage sizelimitations imposed on web technologies, the new content item can bestored to local storage 220 because the data storage operation is beingperformed by native layer 214 using native APIs of mobile device 210.

In some implementations, web view 216 can be configured to manage userinterfaces and communicate with content management system 106. Forexample, because web view 216 is implemented using various webtechnologies, such as JavaScript, HTML, cascading style sheets, etc.,the user interfaces for content authoring application 212 are easier tocreate by developers. Moreover, since the web technologies are platformindependent, the web code used by web view 216 can be written once(e.g., per version of the application) and used across a variety ofcomputing platforms. Additionally, since the web code is provided usingclient resource bundle 220, software updates can be performed by simplyreplacing client resource bundle 220 and without reinstalling orupdating native layer 214 of content authoring application 212. Thus,interactions between content authoring application 212 and mobile device210 can be performed using efficient native interfaces, while coregraphical user interfaces, the core application data model, and networkcommunications can be performed using easy to use (and reuse) and easyto implement web technologies.

In some implementations, native bridge 302 can implement a native bridgeprotocol for handling a variety of message types. For example, while thedata type of the messages exchanged between native layer 214 and webview 216 is a string, the string can be encoded with data describingspecific message types and corresponding payloads. For example, thenative bridge protocol can include a “get content item” message type forgetting a content item by identifier and type. Web view 216 can, forexample, generate a message string that identifies the message type(e.g., “getItem”), specifies an identifier for the content item (e.g.,“contentItem1”, string identifier, URL, etc.), and specifies a type forthe content item (e.g., “note”). For example, the message string canlook like the following: “getItem: contentItem1, note.” Web view 216 canstore the string in the global variable (e.g., “Bridge”) and navigatethe empty iframe to the predefined URL (e.g., “data://_QUEUE_MESSAGE_”)to notify native layer 214 that a new message has been sent by web view216 (e.g., sent by the web technology running in web view 216).

In some implementations, native layer 214 can intercept the navigationof the empty iframe to the predefined URL and retrieve the message fromthe global variable in response to the navigation. Native layer 214 canparse the message string to determine the operation requested by webview 216. For example, native layer 214 can parse the string todetermine that web view 216 is requesting that native layer 214 get acontent item associated with the specified identifier and/or contentitem type. Native layer 214 can retrieve the content item matching thespecified identifier and/or content item type from local content storage220. Native layer 214 can encode the content item into a message stringthat identifies the content item and includes the content of the contentitem (e.g., “contentItem1: content”). Native layer 214 can store themessage string in the global variable, as described above. After nativelayer 214 stores the message string in the global variable, web view 216can receive a notification that the value of the global variable haschanged. Web view 216 can obtain the message string from the globalvariable and parse the message string to obtain the requested contentitem.

Similarly, native bridge 302 can provide for getting all items of aspecified content item type. For example, web view 216 can send amessage (e.g., “getAllItems: type”) to native layer 214 to get allcontent items corresponding to a specified content item type (e.g.,“note”). Native layer 214 can find all content items in content storage220 corresponding to the specified content item type and send the foundcontent items to web view 216 using native bridge 302, as describedabove.

In some implementations, native bridge 302 can provide a mechanism thatallows web view 216 to store content items to local content storage 220using native layer 214. For example, the native bridge protocol candefine messages for storing a content item to local content storage 220and/or updating a content item in local content storage 220. The storeand update messages can include a content item identifier, a contentitem type, and a value. The value can include the content of theidentified content item to be stored or updated. These messages can beencoded into message strings, as described above. For example, to storea new content item, web view 216 can generate a string that includes themessage type, the content item identifier, the content item type, andthe content value (e.g., “setItem: contentItem2, note, content”). Tostore an update to a content item, web view 216 can generate a stringthat includes the message type, the content item identifier, the contentitem type, and the content value (e.g., “updateItem: contentItem2, note,content”). Web view 216 can send the message string to native layer 214using the native bridge protocol described above. Upon receipt of themessage from web view 216, native layer 214 can perform the requestedstorage or update operation to store or update the specified contentitem in content storage 220 based on content parsed from the receivedmessage.

In some implementations, native bridge 302 can provide a mechanism thatallows web view 216 to delete content items from local content storage220 using native layer 214. For example, the native bridge protocol candefine messages for deleting a content item from local content storage220 (e.g., “removeItem”) and/or deleting all content items from localcontent storage 220 (e.g., “clear”). The remove item message can includea content item identifier and/or a content item type. The clear messagehas no parameters. In response to receiving a message string from webview 216 indicating that web view 216 is requesting deletion of acontent item (e.g., “removeItem: contentItem3, note”), native layer 214can delete the specified content item from local content storage 220. Inresponse to receiving a message string from web view 216 indicating thatweb view 216 is requesting deletion of all content items (e.g.,“clear”), native layer 214 can delete the all content items from localcontent storage 220. Thus, native bridge 302 can implement protocols forcommunicating between web view 216 and native layer 214 so that the webtechnologies of web view 216 can take advantage of native API accessavailable to native layer 214.

FIG. 4 is a component interaction diagram illustrating an exampleprocess 400 for updating a hybrid application. For example, a user caninvoke (402) content authoring application 212. Upon invocation ofcontent authoring application 402, native layer 214 can load (404) webview 216. For example, web view 216 can be a JavaScript engine, webbrowser, etc., contained within content authoring application 212 and/orwithin native layer 214. The functionality provided by web view 216 isdefined by web code (e.g., JavaScript, HTML, CSS, etc.) that is loadedinto web view 216. For example, web view 216 can load (406) localresource bundle 220 using native wrapper 228 and execute web code topresent a graphical user interface and/or provide other functionality asdefined by resources 226 (e.g., JavaScript files, HTML files, etc.).

After loading the local resource bundle, web view 216 can create (408)the native bridge to facilitate communication between web view 216 andnative layer 214. For example, resources 226 can include web code (e.g.,JavaScript) that creates a global variable for communicating between webview 216 and native layer 214. The web code can create the iframe thatis used by web view 216 to notify native layer 214 that a new message isavailable from web view 216. After the bundle is loaded and the nativebridge is created, web view 216 can use the native bridge to send (410)a connection established message to native layer 214 indicating that webview 216 has been successfully initiated and that the native bridge isoperational.

In some implementations, web view 216 can determine whether a softwareupdate is available for web view 216. For example, web view 216 can senda message (412) to content authoring module 202 of content managementsystem 106 to request version update information. For example, therequest can be a specific request for current version information. Therequest can be part of another request for information. For example, webview 216 can request a content item from content authoring module 202.The header of the content item request can include informationidentifying the version of content authoring application 212 installedon mobile device 210. When web view 216 loads resource bundle 220, webview 216 can obtain the version information for local resource bundle220 from native configuration 222. Web view 216 can send the versioninformation (e.g., version identifier) for local resource bundle 220 tocontent authoring module 202. Content authoring module 202 can determinewhether the version of local resource bundle 220 matches (e.g.,corresponds to, is the same as, etc.) the current version of resourcebundle 204 on content management system 106. When the versions match(e.g., local resource bundle 220 corresponds to the latest version ofresource bundle 204), content authoring module 202 can send a message toweb view 216 indicating that local resource bundle 220 is the most up todate version available.

When the versions do not match (e.g., local resource bundle 220 is outof date), content authoring module 202 can send a message (414) to webview 216 that includes the native configuration file for client resourcebundle 204. As described above, the native configuration file caninclude a version identifier for the updated version of contentauthoring application 210, and a list of resources for the updatedversion of content authoring application 210. In some implementations,the list of resources can include for each resource a resourceidentifier (e.g., name, URL, etc.) and/or a timestamp corresponding tothe last update to the resource. After receiving the updated nativeconfiguration file, web view 216 can request (e.g., through nativebridge 302) that native layer 214 store (416) the native configurationfile to local storage on mobile device 210.

In some implementations, web view 216 can determine (418) whichindividual resources in client resource bundle 220 on mobile device 210should be updated. For example, after receiving the updated nativeconfiguration file from content authoring module 202, web view 216 cancompare the updated native configuration file to local nativeconfiguration file 222 to determine which resources have been changed.For example, web view 216 can compare the respective timestamps of eachresource to determine whether the timestamps differ between the updatednative configuration file and local native configuration file 222. Whenweb view 216 identifies a resource where the timestamp in local nativeconfiguration file 222 differs from the updated native configurationfile or when web view 216 identifies a resource in the updated nativeconfiguration file that does not exist in local native configurationfile 222, then web view 216 can request (420) the identified resourcefrom content authoring module 202. For example, web view 216 can makemultiple requests for updated or new resources depending on how manyresource updates are identified in the updated native configurationfile. Updating resources individually rather than updating the entireclient resource bundle provides for more efficient use of bandwidth(e.g., only changed files are transmitted) and allows for resuming theupdate if the network connection is interrupted.

In some implementations, web view 216 can receive (422) the updatedresource from content authoring module 202. For example, web view 216can receive an updated resource in response to each resource request.After receiving a resource update (e.g., after each resource is receivedor after all resources are received), web view 216 can request (e.g.,through native bridge 302) that native layer 214 store each resource inlocal storage on mobile device 210.

In some implementations, web view 216 can dynamically update web view216 with the updated resources while web view 216 is running. Forexample, after storing the updated resources (e.g., now local clientresource bundle 220) to local storage, web view 216 can reload localclient resource bundle 220 to load the updated resources and execute theupdated web code. For example, web view 216 can reload client resourcebundle 220 when performing a navigation operation (e.g., to a new webpage, URL, etc.) so that the transition appears seamless to the user.After loading the updated resource, web view 216 can, for example,present an updated graphical user interface having new functionality forthe user to use. Thus, content authoring application 212 can be updatedwhile continuing to run and without needing to update the native code innative layer 214. Moreover, by storing client resource bundle 220locally on mobile device 210, client authoring application 212 can beused by the user even when mobile device 210 is offline.

FIG. 5 is a component interaction diagram illustrating an exampleprocess 500 for native file storage in a hybrid application. Forexample, a user can invoke (502) content authoring application 212. Uponinvocation of content authoring application 402, native layer 214 canload (504) web view 216. For example, web view 216 can be a JavaScriptengine, web browser, etc., contained within content authoringapplication 212 and/or within native layer 214. The functionalityprovided by web view 216 is defined by web code (e.g., JavaScript, HTML,CSS, etc.) that is loaded into web view 216. For example, web view 216can load (506) local resource bundle 220 using native wrapper 228 andexecute web code to present a graphical user interface and/or provideother functionality as defined by resources 226 (e.g., JavaScript files,HTML files, etc.).

After loading the local resource bundle, web view 216 can create (508)the native bridge to facilitate communication between web view 216 andnative layer 214. For example, resources 226 can include web code (e.g.,JavaScript) that creates a global variable for communicating between webview 216 and native layer 214. The web code can create the iframe thatis used by web view 216 to notify native layer 214 that a new message isavailable from web view 216. After the bundle is loaded and the nativebridge is created, web view 216 can use the native bridge to send (510)a connection established message to native layer 214 indicating that webview 216 has been successfully initiated and that the native bridge isoperational.

After web view 216 is running (e.g., as indicated by the connectionestablished message), native layer 214 can send a message (512) to webview 216 (e.g. through the native bridge) to cause web view 216 to loada content item list. For example, the content item list can includecontent items created and/or managed by content authoring application212. The content item list can be loaded as part of the initializationprocess of content authoring application 212 so that web view 216 canpresent the list to the user so that the user can select content itemsto edit using content authoring application 212. The content item listcan be loaded so that web view 216 can update content items storedlocally in content storage 220.

In response to receiving the load content item list message from nativelayer 214, web view 216 can request (514) the content item list fromcontent authoring module 202 of content management system 106. Inresponse (516), content authoring module 202 can send a list of contentitems associated with the user and available for editing with (e.g.,compatible with) content authoring application 212.

In some implementations, web view 216 can update local content storage220 with content items in the received content item list. For example,after web view receives the content item list from content authoringmodule 202, web view 216 can request (e.g., through the native bridge) alocal content item list (518) from native layer 214. The local contentitem list can, for example, include a list of content items associatedwith content authoring application 212 and stored locally in contentstorage 220. Native layer 214 can generate the local content item listand send the content item list (520) to web view 216 through the nativebridge.

After receiving the local content item list and the server content itemlist (e.g., from content authoring module 202), web view 216 can comparethe two lists to determine (522) which content items have been added,modified, or deleted from content management system 106. For example,when the local content item list includes a particular content item andthe server content item list does not, web view 216 can send a request(523) to native layer 214 to remove (e.g., delete) the particularcontent item.

When the local content item list does not include a particular contentitem that is included in the server content item list, web view 216 cansend a message (524) to content authoring module 202 requesting theparticular content item. Content authoring module 202 can respond bysending (526) the requested content item to web view 216. Similarly,when a timestamp for a particular content item in the local content itemlist does not match the corresponding content item in the server contentitem list, web view 216 can send a message (524) to content authoringmodule 202 requesting updates for the particular content item. Contentauthoring module 202 can respond by sending (526) the requested contentitem updates to web view 216. Web view 216 can, in turn, send a message(528) to native layer 214 through the native bridge to store or updatethe particular content item in local content storage 220. In response toreceiving the message from web view 216, native layer 214 can store orupdate (530) the content item in local content storage 220. Thus,content authoring application 212 can keep the content items stored inlocal content storage 220 updated so that content authoring application212 can provide for offline access to the content items associated withcontent authoring application 212.

FIG. 6 is a component interaction diagram illustrating an exampleprocess 600 for working offline in a hybrid application. For example, auser can invoke (602) content authoring application 212. Upon invocationof content authoring application 402, native layer 214 can load (604)web view 216. For example, web view 216 can be a JavaScript engine, webbrowser, etc., contained within content authoring application 212 and/orwithin native layer 214. The functionality provided by web view 216 isdefined by web code (e.g., JavaScript, HTML, CSS, etc.) that is loadedinto web view 216 from client local resource bundle 220. For example,web view 216 can load (606) local resource bundle 220 using nativewrapper 228 and execute web code to present a graphical user interfaceand/or provide other functionality as defined by resources 226 (e.g.,JavaScript files, HTML files, etc.).

After loading the local resource bundle, web view 216 can create (608)the native bridge to facilitate communication between web view 216 andnative layer 214. For example, resources 226 can include web code (e.g.,JavaScript) that creates a global variable for communicating between webview 216 and native layer 214. The web code can create the iframe thatis used by web view 216 to notify native layer 214 that a new message isavailable from web view 216. After the bundle is loaded and the nativebridge is created, web view 216 can use the native bridge to send (610)a connection established message to native layer 214 indicating that webview 216 has been successfully initiated and that the native bridge isoperational.

After web view 216 is running (e.g., as indicated by the connectionestablished message), native layer 214 can send a message (512) to webview 216 (e.g., through the native bridge) to cause web view 216 to loada content item list. For example, the content item list can includecontent items created and/or managed by content authoring application212. The content item list can be loaded as part of the initializationprocess of content authoring application 212 so that web view 216 canpresent the list to the user so that the user can select content itemsto edit using content authoring application 212. The content item listcan be loaded so that web view 216 can update content items storedlocally in content storage 220.

However, instead of requesting a content item list from contentauthoring module 202 as described in process 500, web view 216 candetermine (614) that mobile device 210 is offline and/or contentauthoring module 202 is unreachable. In response to determining thatcontent authoring module 202 is unreachable, web view 216 can send amessage (616) through the native bridge to native layer 214 requestingthat native layer 214 send web view 216 a local content item listidentifying the content items stored locally in content store 220.Native layer 214 can generate a list of locally stored content itemsassociated with content authoring application 212 and send the list toweb view 216 through the native bridge. After receiving the localcontent item list, web view 216 can present the local content item liston a graphical user interface presented by web view 216 according to theinstructions provided by resources 226 of client resource bundle 220 onmobile device 210.

In some implementations, web view 216 can present a local content item.For example, after presenting the list of local content items, web view216 can receive a user selection of a content item from the list oflocal content items. In response to receiving the selection, web view216 through local bridge 302 can request the selected content item fromnative layer 214. Native layer 214 can obtain the requested content itemfrom local content storage 220 and send (626) the requested localcontent item to web view 216. After receiving the requested localcontent item, web view 216 can present (628) the local content item forreview and/or editing by the user of content authoring application 212.Thus, even though mobile device 210 is offline and/or content authoringmodule 202 is unreachable, web view 216 can still present graphical userinterfaces, present content items, and/or perform other operationsbecause everything needed to execute (e.g., run, present, operate, etc.)web view 216 and present content items is stored locally on mobiledevice 210.

FIG. 7 is an example process 700 for updating a hybrid application. Forexample, process 700 can update the web code of the hybrid applicationwhile the hybrid application is running and without modifying the nativecode of the hybrid application.

At step 702, mobile device 210 can execute native software correspondingto a hybrid application installed on the mobile device. For example, thenative software can correspond to native layer 214, described above. Thenative software can be platform-specific in that the software can becompiled and/or built for a specific operating system, processor, orsystem configuration used or implemented by mobile device 210.

At step 704, mobile device 210 can obtain a resource bundle for thehybrid application stored on mobile device 210. For example, when thehybrid application is installed on mobile device 210, the installationcan include storing on mobile device 210 a resource bundle that includesthe resources needed to execute a web view within the hybridapplication.

At step 706, mobile device 210 can load web code from the resourcebundle into the hybrid application. For example, the web code caninclude various platform independent web technologies, such as HTML,JavaScript, CSS, etc. The native software can include a web engine(e.g., web browser, JavaScript engine, compiler, interpreter, etc.) thatcan read, compile, and/or execute the web code. Mobile device 210 canload the web code from the resource bundle into the web engine when thehybrid application is initialized by loading a web page (e.g., a localnative wrapper HTML file) that references the resources in the resourcebundle.

At step 708, mobile device 210 can execute the web code. For example,the web engine in the native software can read, compile and/or executethe web code (e.g., web view 216) to present graphical user interfaces,manage and/or manipulate data, and communicate with web servers, such ascontent authoring module 202 of content management system 106.

At step 710, mobile device 210 can obtain resource bundle updateinformation from a network resource. For example, when the hybridapplication communicates with a corresponding web server, the hybridapplication can send version information identifying the version of thehybrid application running on mobile device 210. When the web serverreceives the version information, the web server can determine whetherthe version of the hybrid application on mobile device 210 correspondsto the latest version of the hybrid application at the web server. Whenthe version of the hybrid application on mobile device 210 does notmatch the latest version of the application on the web server, the webserver can send an updated resource bundle to the hybrid application.For example, the web server can send configuration data identifying thelatest version of the hybrid application and the resources correspondingto the latest version of the hybrid application.

At step 712, mobile device 210 can update the web code of the hybridapplication based on the resource bundle update while leaving the nativesoftware unchanged. For example, the mobile device 210 can determinewhich resources in the resource bundle are out of date based on theconfiguration data. Mobile device 210 can then request the resourcesthat are required to update the hybrid application, as described above.Mobile device 210 can replace the out of date resources in the localresource bundle stored on mobile device 210 with the newly updatedresources.

At step 714, mobile device 210 can execute the updated web code from theupdated resource bundle. For example, the web engine can reload theresource bundle and execute the updated web code in the updatedresources to allow the user to access the updated features of the hybridapplication. Thus, mobile device 210 can update the hybrid applicationwhile the hybrid application is running and without modifying the nativesoftware of the hybrid application.

FIG. 8 is an example process 800 for providing access to a hybridapplication offline. For example, by storing the web code, resources,and/or content items locally on mobile device 210, a hybrid applicationthat typically depends on obtaining the web code, resources, and/orcontent items from a network resource can be executed by mobile device210 even when mobile device 210 is not connected to a network.

At step 802, mobile device 210 can invoke a native layer of the hybridapplication on the mobile device. For example, the native layer cancorrespond to native layer 214, described above. The native layer caninclude platform-specific software in that the software can be compiledand/or built for a specific operating system, processor, or systemconfiguration used or implemented by mobile device 210.

At step 804, mobile device 210 can load a web view into the applicationfrom storage on mobile device 210. For example, the web view cancorrespond to web view 216, described above. The web view can include aweb engine implemented using native software in native layer 214 and webcode that is executed by the web engine to provide functionality,features, etc., to the hybrid application. The web code can be loadedinto the web engine from a local resource bundle so that the hybridapplication can function even when mobile device 210 is not connected toa network or corresponding network server.

At step 806, mobile device 210 can receive a request for a content itemstored on a network server. For example, the hybrid application canreceive user input requesting to view or edit a content item stored onthe network server. The native layer of the hybrid application canrequest that the web view download content items from the network serverto update the content items stored locally on mobile device 210, asdescribed above.

At step 808, mobile device 210 can determine that the mobile devicecannot connect to the network server. For example, the hybridapplication (e.g., web view 216) can determine that mobile device 210 isnot connected to a network and/or that the network server isunreachable.

At step 810, mobile device 210 can request a locally stored version ofthe requested content item from the native layer of the hybridapplication. For example, in response to determining that the networkserver is unreachable, web view 216 can send a message to native layer214 requesting the content item from local storage on mobile device 210.

At step 812, mobile device 210 can obtain a locally stored version ofthe requested content item. For example, native layer 214 can obtain thelocally stored version of the requested content item from local contentstorage 220.

At step 814, mobile device 210 can send the locally stored version ofthe requested content item to web view 216. For example, native layer214 can send the locally stored version of the requested content item toweb view 216 through native bridge 302. Native layer 214 can, forexample, encode the content item (e.g., content item identifier andcontents) into a message string and send the message string to web view216 using native bridge 302, as described above.

At step 816, mobile device 210 can present the requested content item ona display of mobile device 210. For example, after web view 216 receivesthe requested content item, web view 216 can present the content item ona graphical user interface generated according to the web code loadedfrom the local resource bundle on mobile device 210.

9A and FIG. 9B show example possible system embodiments. The moreappropriate embodiment will be apparent to those of ordinary skill inthe art when practicing the present technology. Persons of ordinaryskill in the art will also readily appreciate that other systemembodiments are possible.

FIG. 9A illustrates a conventional system bus computing systemarchitecture 900 wherein the components of the system are in electricalcommunication with each other using a bus 905. Example system 900includes a processing unit (CPU or processor) 910 and a system bus 905that couples various system components including the system memory 915,such as read only memory (ROM) 920 and random access memory (RAM) 925,to the processor 910. The system 900 can include a cache of high-speedmemory connected directly with, in close proximity to, or integrated aspart of the processor 910. The system 900 can copy data from the memory915 and/or the storage device 930 to the cache 912 for quick access bythe processor 910. In this way, the cache can provide a performanceboost that avoids processor 910 delays while waiting for data. These andother modules can control or be configured to control the processor 910to perform various actions. Other system memory 915 may be available foruse as well. The memory 915 can include multiple different types ofmemory with different performance characteristics. The processor 910 caninclude any general purpose processor and a hardware module or softwaremodule, such as module 1 932, module 2 934, and module 3 936 stored instorage device 930, configured to control the processor 910 as well as aspecial-purpose processor where software instructions are incorporatedinto the actual processor design. The processor 910 may essentially be acompletely self-contained computing system, containing multiple cores orprocessors, a bus, memory controller, cache, etc. A multi-core processormay be symmetric or asymmetric.

To enable user interaction with the computing device 900, an inputdevice 945 can represent any number of input mechanisms, such as amicrophone for speech, a touch-sensitive screen for gesture or graphicalinput, keyboard, mouse, motion input, speech and so forth. An outputdevice 935 can also be one or more of a number of output mechanismsknown to those of skill in the art. In some instances, multimodalsystems can enable a user to provide multiple types of input tocommunicate with the computing device 900. The communications interface940 can generally govern and manage the user input and system output.There is no restriction on operating on any particular hardwarearrangement and therefore the basic features here may easily besubstituted for improved hardware or firmware arrangements as they aredeveloped.

Storage device 930 is a non-volatile memory and can be a hard disk orother types of computer readable media which can store data that areaccessible by a computer, such as magnetic cassettes, flash memorycards, solid state memory devices, digital versatile disks, cartridges,random access memories (RAMs) 925, read only memory (ROM) 920, andhybrids thereof.

The storage device 930 can include software modules 932, 934, 936 forcontrolling the processor 910. Other hardware or software modules arecontemplated. The storage device 930 can be connected to the system bus905. In one aspect, a hardware module that performs a particularfunction can include the software component stored in acomputer-readable medium in connection with the necessary hardwarecomponents, such as the processor 910, bus 905, display 935, and soforth, to carry out the function.

FIG. 9B illustrates a computer system 950 having a chipset architecturethat can be used in executing the described method and generating anddisplaying a graphical user interface (GUI). Computer system 950 is anexample of computer hardware, software, and firmware that can be used toimplement the disclosed technology. System 950 can include a processor910, representative of any number of physically and/or logicallydistinct resources capable of executing software, firmware, and hardwareconfigured to perform identified computations. Processor 910 cancommunicate with a chipset 960 that can control input to and output fromprocessor 910. In this example, chipset 960 outputs information tooutput 965, such as a display, and can read and write information tostorage device 970, which can include magnetic media, and solid statemedia, for example. Chipset 960 can also read data from and write datato RAM 975. A bridge 980 for interfacing with a variety of userinterface components 985 can be provided for interfacing with chipset960. Such user interface components 985 can include a keyboard, amicrophone, touch detection and processing circuitry, a pointing device,such as a mouse, and so on. In general, inputs to system 950 can comefrom any of a variety of sources, machine generated and/or humangenerated.

Chipset 960 can also interface with one or more communication interfaces990 that can have different physical interfaces. Such communicationinterfaces can include interfaces for wired and wireless local areanetworks, for broadband wireless networks, as well as personal areanetworks. Some applications of the methods for generating, displaying,and using the GUI disclosed herein can include receiving ordereddatasets over the physical interface or be generated by the machineitself by processor 910 analyzing data stored in storage 970 or 975.Further, the machine can receive inputs from a user via user interfacecomponents 985 and execute appropriate functions, such as browsingfunctions by interpreting these inputs using processor 910.

It can be appreciated that example systems 900 and 950 can have morethan one processor 910 or be part of a group or cluster of computingdevices networked together to provide greater processing capability.

For clarity of explanation, in some instances the present technology maybe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

Any of the steps, operations, functions, or processes described hereinmay be performed or implemented by a combination of hardware andsoftware modules, alone or in combination with other devices. In anembodiment, a software module can be software that resides in memory ofa client device and/or one or more servers of a content managementsystem and perform one or more functions when a processor executes thesoftware associated with the module. The memory can be a non-transitorycomputer-readable medium.

In some embodiments the computer-readable storage devices, mediums, andmemories can include a cable or wireless signal containing a bit streamand the like. However, when mentioned, non-transitory computer-readablestorage media expressly exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, flash memory, USB devices provided with non-volatile memory,networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include laptops,smart phones, small form factor personal computers, personal digitalassistants, and so on. Functionality described herein also can beembodied in peripherals or add-in cards. Such functionality can also beimplemented on a circuit board among different chips or differentprocesses executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims.

1. A method comprising: storing, by a computing device, a software application in memory of the computing device, where the software application includes a native component and a resource bundle, where the native component is generated using technologies native to the computing device, and where the resource bundle includes non-native web code defining a web view for the software application; receiving, by the computing device, user input selecting the software application; in response to receiving the user input, executing, by the computing device, the native component of the software application; upon execution of the native component, loading, by the computing device, web code from the stored resource bundle into the native component to generate the web view; presenting the web view on a display of the computing device; determining, by the computing device, a first version identifier for the stored resource bundle; sending, by the computing device, a message from the web view to the server device including the first version identifier, where the server device determines whether the first version identifier corresponds to the latest version of the resource bundle; and receiving, by the computing device from server device, update data when the first version identifier is different than a second version identifier corresponding to a latest version of the resource bundle; and while the software application continues to execute: automatically updating, by the computing device, the stored resource bundle to correspond to the latest version of the resource bundle based on the update data; automatically reloading, by the computing device, web code from the updated resource bundle into the native component to generate an updated web view; and presenting the updated web view on a display of the computing device.
 2. (canceled)
 3. The method of claim 1, further comprising: determining, based on the update data, that the latest version of the resource bundle includes an updated version of a first resource in the stored resource bundle; receiving the updated version of the first resource from the server device; and replacing a stored version of the first resource with the updated version of the first resource on the computing device.
 4. The method of claim 3, further comprising: after replacing the stored version of the first resource with the updated version of the first resource and while the software application continues to execute, reloading the web code from the stored resource bundle, including the updated version of the first resource, into the native component to generate an updated web view; and presenting the updated web view on a display of the computing device.
 5. The method of claim 1, wherein the native component continues to execute while the stored resource bundle is updated on the computing device.
 6. The method of claim 1, wherein the native component remains unchanged when the stored resource bundle is updated on the computing device.
 7. The method of claim 4, wherein the updated version of the first resource is received by the web view, and further comprising: receiving, by the native component, the update version of the first resource from the web view when the web view navigates to a particular web address; and storing, by the native component, the updated version of the first resource received from the web view in the stored resource bundle.
 8. A non-transitory computer readable medium including one or more sequences of instructions that, when executed by one or more processors, cause the processors to perform operations comprising: storing, by a computing device, a software application in memory of the computing device, where the software application includes a native component and a resource bundle, where the native component is generated using technologies native to the computing device, and where the resource bundle includes non-native web code defining a web view for the software application; executing, by the computing device, the native component of the software application; upon execution of the native component, loading, by the computing device, web code from the stored resource bundle into the native component to generate the web view; presenting the web view on a display of the computing device; determining, by the computing device, a first version identifier for the stored resource bundle: sending, by the computing device, a message from the web view to the server device including the first version identifier, where the server device determines whether the first version identifier corresponds to the latest version of the resource bundle; and receiving, by the computing device from server device, update data when the first version identifier is different than a second version identifier corresponding to a latest version of the resource bundle; and while the software application continues to execute: automatically updating, by the computing device, the stored resource bundle to correspond to the latest version of the resource bundle based on the update data; automatically reloading, by the computing device, web code from the updated resource bundle into the native component to generate an updated web view; and presenting the updated web view on a display of the computing device.
 9. (canceled)
 10. The non-transitory computer readable medium of claim 8, wherein the instructions cause the processors to perform operations comprising: determining, based on the update data, that the latest version of the resource bundle includes an updated version of a first resource in the stored resource bundle; receiving the updated version of the first resource from the server device; and replacing a stored version of the first resource with the updated version of the first resource on the computing device.
 11. The non-transitory computer readable medium of claim 10, wherein the instructions cause the processors to perform operations comprising: after replacing the stored version of the first resource with the updated version of the first resource and while the software application continues to execute, reloading the web code from the stored resource bundle, including the updated version of the first resource, into the native component to generate an updated web view; and presenting the updated web view on a display of the computing device.
 12. The non-transitory computer readable medium of claim 8, wherein the native component continues to execute while the stored resource bundle is updated on the computing device.
 13. The non-transitory computer readable medium of claim 8, wherein the native component remains unchanged when the stored resource bundle is updated on the computing device.
 14. The non-transitory computer readable medium of claim 11, wherein the updated version of the first resource is received by the web view, and wherein the instructions cause the processors to perform operations comprising: receiving, by the native component, the update version of the first resource from the web view when the web view navigates to a particular web address; and storing, by the native component, the updated version of the first resource received from the web view in the stored resource bundle.
 15. A system comprising: one or more processors; and a non-transitory computer readable medium including one or more sequences of instructions that, when executed by the one or more processors, cause the processors to perform operations comprising: storing, by the system, a software application in memory of the computing device, where the software application includes a native component and a resource bundle, where the native component is generated using technologies native to the computing device, and where the resource bundle includes non-native web code defining a web view for the software application; executing, by the system, the native component of the software application; upon execution of the native component, loading, by the system, web code from the stored resource bundle into the native component to generate the web view; presenting the web view on a display of the computing device; determining, by the computing device, a first version identifier for the stored resource bundle; sending, by the computing device, a message from the web view to the server device including the first version identifier, where the server device determines whether the first version identifier corresponds to the latest version of the resource bundle; and receiving, by the computing device from server device, update data when the first version identifier is different than a second version identifier corresponding to a latest version of the resource bundle; and while the software application continues to execute: based on the update date, determining one or more resources in the resource bundle to update; obtaining the one or more resources from the server device; automatically updating, by the system, the stored resource bundle to include the one or more resources; automatically reloading, by the system, web code from the updated resource bundle into the native component to generate an updated web view; and presenting the updated web view on a display of the computing device.
 16. (canceled)
 17. The system of claim 15, wherein the instructions cause the processors to perform operations comprising: determining, based on the update data, that the latest version of the resource bundle includes an updated version of a first resource in the stored resource bundle; receiving the updated version of the first resource from the server device; and replacing a stored version of the first resource with the updated version of the first resource on the computing device.
 18. The system of claim 17, wherein the instructions cause the processors to perform operations comprising: after replacing the stored version of the first resource with the updated version of the first resource and while the software application continues to execute, reloading the web code from the stored resource bundle, including the updated version of the first resource, into the native component to generate an updated web view; and presenting the updated web view on a display of the computing device.
 19. The system of claim 15, wherein the native component continues to execute while the stored resource bundle is updated on the computing device.
 20. The system of claim 15, wherein the native component remains unchanged when the stored resource bundle is updated on the computing device. 